Release monitoring through check-in and tethering system

ABSTRACT

A check-in and tethering system for monitoring persons such as released in court-ordered supervised programs and a method for operating such a system is disclosed. The system includes a tethered mobile device that provides a check-in procedure that requires a response from a user of the tethered mobile device in the form of at least one of a device identifier from a monitored tethered device attached to the user, a biometric response, or a performed action by the user. The tethered mobile device determines whether the response is valid and transmits a notification to a monitoring center in response to the determination.

BACKGROUND Field

This disclosure relates to monitoring persons such as those released oncourt-ordered supervised programs using a check-in and tethering system.

Background

In certain situations, persons that are released from custody arerequired to be electronically monitored outside of a controlledenvironment. To monitor the released persons, jurisdictions typicallyare limited to options having issues that are expensive, inflexible, andinconvenient. One option is a home-based device which is a devicepermanently placed in a residence of the monitored person and whichcommunicates with a device that is attached to the monitored person.Because it relies on a home-based device, this implementation confinesthe monitored person to their residence and any sort of travel away fromthe residence, such as visits to the doctor or probation officer, couldcause an alarm. Accordingly, this implementation does not accommodatethe monitored person leaving his residence such as for work release orcommunity service work. Another option relies on global positioningsystem (GPS) where the device attached to the monitored person is a GPScommunications device that transmits the location of the offender bycellular transmission to the jurisdiction for position monitoring.However, GPS communications devices are bulky, expensive as they requirea cellular connection, and require more frequent charges of theirbattery.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate embodiments of the present disclosureand, together with the description, further serve to explain theprinciples of the disclosure and to enable a person skilled in thepertinent art to make and use the embodiments.

FIG. 1 illustrates a block diagram of an exemplary tethering monitoringsystem, according to embodiments of the present disclosure.

FIG. 2 illustrates a block diagram of an exemplary tethered mobiledevice for use in the exemplary tethering monitoring system of FIG. 1,according to embodiments of the present disclosure.

FIG. 3 illustrates an exemplary tethered monitoring device for use inthe exemplary tethering monitoring system of FIG. 1, according toembodiments of the present disclosure.

FIG. 4 illustrates a flowchart diagram of an exemplary method forexecuting a check-in procedure in an exemplary tethered mobile device ofFIG. 2, according to embodiments of the present disclosure.

FIG. 5 illustrates a flowchart diagram of an exemplary method fortracking an authorized trip itinerary for the exemplary tethered mobiledevice of FIG. 2 in the exemplary tethering monitoring system of FIG. 1,according to embodiments of the present disclosure.

FIG. 6 illustrates a flowchart diagram of an exemplary method fordetermining when to initiate a check-in procedure in the exemplarytethering monitoring system of FIG. 1, according to embodiments of thepresent disclosure.

FIG. 7 illustrates a block diagram of an of an exemplary method forperforming real-time verification of a monitored person in an exemplarytethered mobile device of FIG. 2 in the exemplary tethering monitoringsystem of FIG. 1, according to embodiments of the present disclosure.

FIG. 8 illustrates a block diagram of a general purpose computer thatmay be used to perform various aspects of the present disclosure.

The present disclosure will be described with reference to theaccompanying drawings. In the drawings, like reference numbers indicateidentical or functionally similar elements. Additionally, the left mostdigit(s) of a reference number identifies the drawing in which thereference number first appears.

DETAILED DESCRIPTION

The following Detailed Description refers to accompanying drawings toillustrate exemplary embodiments consistent with the disclosure.References in the Detailed Description to “one exemplary embodiment,”“an exemplary embodiment,” “an example exemplary embodiment,” etc.,indicate that the exemplary embodiment described may include aparticular feature, structure, or characteristic, but every exemplaryembodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same exemplary embodiment. Further, when a particularfeature, structure, or characteristic is described in connection with anexemplary embodiment, it is within the knowledge of those skilled in therelevant art(s) to affect such feature, structure, or characteristic inconnection with other exemplary embodiments whether or not explicitlydescribed.

The exemplary embodiments described herein are provided for illustrativepurposes, and are not limiting. Other exemplary embodiments arepossible, and modifications may be made to the exemplary embodimentswithin the spirit and scope of the disclosure. Therefore, the DetailedDescription is not meant to limit the disclosure. Rather, the scope ofthe disclosure is defined only in accordance with the following claimsand their equivalents.

Embodiments may be implemented in hardware (e.g., circuits), firmware,software, or any combination thereof. Embodiments may also beimplemented as instructions stored on a machine-readable medium, whichmay be read and executed by one or more processors. A machine-readablemedium may include any mechanism for storing or transmitting informationin a form readable by a machine (e.g., a computing device). For example,a machine-readable medium may include read only memory (ROM); randomaccess memory (RAM); magnetic disk storage media; optical storage media;flash memory devices; electrical, optical, acoustical or other forms ofpropagated signals (e.g., carrier waves, infrared signals, digitalsignals, etc.), and others. Further, firmware, software, routines,instructions may be described herein as performing certain actions.However, it should be appreciated that such descriptions are merely forconvenience and that such actions in fact result from computing devices,processors, controllers, or other devices executing the firmware,software, routines, instructions, etc. Further, any of theimplementation variations may be carried out by a general purposecomputer, as described below.

For purposes of this discussion, any reference to the term “module”shall be understood to include at least one of software, firmware, andhardware (such as one or more circuit, microchip, or device, or anycombination thereof), and any combination thereof. In addition, it willbe understood that each module may include one, or more than one,component within an actual device, and each component that forms a partof the described module may function either cooperatively orindependently of any other component forming a part of the module.Conversely, multiple modules described herein may represent a singlecomponent within an actual device. Further, components within a modulemay be in a single device or distributed among multiple devices in awired or wireless manner.

The following Detailed Description of the exemplary embodiments will sofully reveal the general nature of the disclosure that others can, byapplying knowledge of those skilled in relevant art(s), readily modifyand/or customize for various applications such exemplary embodiments,without undue experimentation, without departing from the spirit andscope of the disclosure. Therefore, such modifications are intended tobe within the meaning and plurality of equivalents of the exemplaryembodiments based upon the teaching and guidance presented herein. It isto be understood that the phraseology or terminology herein is for thepurpose of description and not of limitation, such that the terminologyor phraseology of the present specification is to be interpreted bythose skilled in relevant art(s) in light of the teachings herein.

Exemplary Tethering Monitoring System

FIG. 1 illustrates a block diagram of an exemplary tethering monitoringsystem 80, according to embodiments of the present disclosure. Tetheringmonitoring system 100 includes a tethering system 110, a tetheringsystem 120, and a monitoring center 130. In some embodiments, tetheringsystem 110 and tethering system 120 represent tethered devices that arerequired to be within a proximity of a user who is to be monitored bymonitoring center 130. Tethering system 110 includes a tetheredmonitoring device 116, a router 118, and at least one tethered mobiledevice 112 and tethered mobile device 114. In some embodiments, tetheredmonitoring device 116 is a device such as a wristband or ankle band thatis physically attached to a user to be monitored. In some embodiments,tethered mobile device 112 is a smartphone and tethered mobile device114 is a tablet.

In some embodiments, tethered monitoring device 116 wirelesslycommunicates with router 118 and/or tethered mobile devices 112 and 114using a wireless communication standard. Examples of wirelesscommunication standards that may be employed in this disclosure includebut are not limited to IEEE 802.11 (otherwise known as “Wi-Fi”),Bluetooth, Bluetooth Low Energy (“BTLE”), or near field communicationsuch as radio frequency identification (“RFID”). For ease andsimplicity, the embodiment will be further discussed with regard totethered mobile device 112. However, it is to be understood that suchdiscussion also applies to tethered mobile devices 114, 122, or 124.

In some embodiments, tethered mobile device 112 initiates a check-inprocedure whereby a user associated with tethered mobile device 112 andtethered monitoring device 116 responds to requests from tethered mobiledevice 112. In some embodiments, the check-in procedure is initiated bya check-in application downloaded and installed on tethered mobiledevice 112. The check-in application is provided by a jurisdiction orauthority, such as monitoring center 130, responsible for monitoring theuser of tethered mobile device 112. Because the check-in applicationassists in monitoring the user, the check-in application is installedand configured in such a manner to prevent the user of tethered mobiledevice 112 from uninstalling or otherwise modifying the check-inapplication. In some embodiments, installation of the check-inapplication results in the creation of a secure area, such as a privatecontainer, in a file system of tethered mobile device 112. The securearea, and therefore, any files such as the check-in application storedtherein, can only be accessed by authorized officials such asadministrators of monitoring center 130. In some embodiments, the securearea is controlled entirely by monitoring center 130.

The check-in application of tethered mobile device 112 initiates thecheck-in procedure based on any number of check-in conditions includingbut not limited to a remote instruction from monitoring center 130, ascheduled check-in request, a random check-in request, or a monitoredcondition of the tethered mobile device 112 (e.g., stationary for apredetermined period of time). The purpose of the check-in procedure isallow monitoring center 130 to verify that the user of tethered mobiledevice 112 is using or within a certain proximity of tethered mobiledevice, to prevent the user from attempting to circumvent monitoring bymonitoring center 130 (e.g., to flee the jurisdiction, to makeunauthorized trips), and to confirm that the user is behaving consistentwith the conditions of his release from custody.

In some embodiments, the check-in procedure includes automated (e.g.,without requiring action from the user) and manual (e.g., requiringaction from the user) check-ins to the check-in application of tetheredmobile device 112. An automated check-in includes a check-in requesttransmitted from tethered mobile device 112 to tethered monitoringdevice 116. In some embodiments, the check-in request is a request fortethered monitoring device 116 to provide a response that allowstethered mobile device 112 to verify that tethered monitoring device 116is within a certain proximity and that it is still operating properly.With regards to proximity, if tethered mobile device 112 and tetheredmonitoring device 116 communicate using near field communications, thentethered monitoring device 116 is ideally within a predetermined rangeof tethered mobile device 112 in order to receive the check-in request.This predetermined range is generally determined by the specificprotocol used such as Bluetooth, BTLE, or RFID. If tethered mobiledevice 112 and tethered monitoring device 116 communicate using Wi-Fi(e.g., through router 118), then tethered mobile device 112 is alsoideally within a predetermined range of tethered mobile device althoughfor Wi-Fi this range is generally larger than the range for near fieldcommunications. Regardless of the protocol, if tethered monitoringdevice 116 is not within the predetermined range, the check-inapplication can perform any number of actions as defined from monitoringcenter 130. The check-in application may initiate a follow-up check-inrequest over the same communication protocol as the first check-inrequest, a follow-up check-in request over a communication protocoldifferent from the protocol used to send the first check-in request,and/or performs a follow-up action such as transmitting an alertnotification to monitoring center 130 indicating that tetheredmonitoring device 116 has not responded to the check-in request.

In some embodiments, a response to the check-in request includes adevice identifier that uniquely identifies tethered monitoring device116. The check-in application verifies that the device identifierreceived in the response is the same as the device identifier that ispre-programmed into the check-in application and also stored in thesecure area, such as a private container, of tethered mobile device 112.Monitoring center 130 configures tethered mobile device 112 to store thedevice identifier that is expected to be communicating with the check-inapplication in the secure area that cannot be accessed by the user.Accordingly, the user of tethered monitoring device 116 cannot access orotherwise see the device identifier. In some embodiments, the check-inrequest also includes other information about operations of the tetheredmonitoring device 116 such as but not limited to battery level andactivity level (e.g., whether the tethered monitoring device 116 hasbeen stationary for a predetermined period of time).

In some embodiments, a manual check-in includes a real-time verificationrequest that generally requires some action to be performed by a user.The performance of the action and/or the results of the action are usedby the check-in application and monitoring center 130 to determinewhether the user is within proximity of or otherwise operating tetheredmobile device 112. In some embodiments, a real-time verification requestis an identity check to verify the identity of the user of tetheredmobile device 114. Examples of real-time verification requests includechallenges to the user such as biometric checks or actions to beperformed by the user. Biometric checks include requiring the user totake a picture of his face using a camera of tethered mobile device 112,place his thumb on a display of tethered mobile device 112, and/or speaka random phrase displayed on tethered mobile device 112. In someembodiments, biometric checks are initiated by the check-in applicationon tethered mobile device. Biometric checks include performing facialrecognition on an image from a camera of tethered mobile device,fingerprint recognition of an fingerprint that is received by thecheck-in application through either the display of tethered mobiledevice 112 or a dedicated fingerprint reader of tethered mobile device,or voice recognition of the user's voice received through a microphoneof tethered mobile device 112. In some embodiments, there is apredetermined response period for the user to response to the identitycheck. If the user does not respond within the predetermined responseperiod, an alert message or notification is transmitted to monitoringcenter 130.

Accordingly, the check-in application includes a camera function, afingerprint reader function, and a voice recorder function, which insome embodiments, is represented as a graphical user interface that aredisplayed on tethered mobile device 112. The camera function controlstethered mobile device 112 to take a picture using any of the cameras ontethered mobile device 112. The fingerprint reader function controlstethered mobile device 112 to display a graphical user interface inwhich the user can place his finger. The voice recorder functioncontrols a microphone and display of tethered mobile device 112. Thedisplay is controlled to display a predetermined phrase that is to berepeated by the user using the microphone of tethered mobile device 112.The predetermined phrase is randomly selected from stored phrases in thesecure area of tethered mobile device 112 or provided remotely bymonitoring center 130. In some embodiments, the check-in applicationrandomly selects which biometric check to perform or can be remotelyselected by monitoring center 130. The purpose of the phrase is toprevent the user from anticipating (and pre-recording his voice) thephrase so that another user could attempt to respond to the biometriccheck using a prerecorded message.

In some embodiments, actions to be performed by the user includeanswering questions (e.g., such as “What is 49+30?”) or specificoperations to be performed using tethered mobile device 112. Examples ofoperations include but are not limited to using the camera of tetheredmobile device 112 to take a picture of tethered monitoring device 116 orany other predetermined object within the user's home such as a clock ora television, sending a text or email message to a predetermined addressassociated with monitoring center 130, or calling a predetermined phonenumber associated with monitoring center 130 and providing a voicesample for verification.

In some embodiments, the check-in application is able to initiate thereal-time verification request and the functions described above absentany input or instruction from the user of tethered mobile device 112. Insome embodiments, the real-time verification request is initiatedautomatically by the check-in application in response to a check-incondition or initiated remotely by monitoring center 130. Accordingly,the check-in application, and by extension, monitoring center 130 havecontrol over operations of tethered mobile device 112 including itscamera, display, and microphones without requiring the user'sauthorization or instructions. A verification response is received inresponse to the verification request and it is determined whether theverification response is a valid or invalid verification response.

In some embodiments, the check-in application sends periodic messages tomonitoring center 130 to ensure that tethered mobile device 112 is stilloperational. A user may attempt to circumvent monitoring by turning offor otherwise disabling his device. If monitoring center 130 fails toreceive a periodic message from tethered mobile device 112, monitoringcenter 130 can initiate the appropriate protocols for tracking andotherwise locating the user.

In some embodiments, the check-in application locks all operations oftethered mobile device 112 until an appropriate response to a check-inis received from tethered monitoring device 116, the user, or both. Forexample, the check-in application is displayed as a graphical userinterface on a display of tethered mobile device 112 during the check-inprocedure. While displayed, the check-in application prevents the userfrom exiting the check-in application, from switching to anotherapplication, or even using any of the other functions of the phone suchas phone calls, text messages, or using the Internet that are notauthorized by the check-in application. For example, during a biometriccheck that involves facial recognition, the check-in application candisable all other inputs of tethered mobile device 112 except for thecamera until an image of the user is received and verified. Similarly,during a biometric check that involves voice recognition, the check-inapplication can disable all inputs of tethered mobile device 112 exceptfor the microphone until a voice recording of the user is received andverified. In this manner, the check-in application allows monitoringcenter 130 to have complete control over tethered mobile device 112 andallows monitoring center 130 to condition operations of tethered mobiledevice 112 on verified responses to check-in requests.

In some embodiments, the user is not required to wear tetheredmonitoring device 116. For example, tethering system 120 includestethered mobile device 112 and tethered mobile device 124. In suchembodiments, tethering system 120 does not implement automated check-insbut does implement manual check-ins as described above.

In some embodiments, tethered monitoring device 116 implements a back-upcommunication subsystem that is activated in response to determiningthat communications with the check-in application of tethered mobiledevice 112 have been interrupted or disabled. Tethered monitoring device116 determines that it can no longer communicate with the check-inapplication in a variety of ways including determining that no responsehas been received in response to an inquiry from tethered monitoringdevice 116 to tethered mobile device 112 or upon not receiving acheck-in request from tethered monitoring device 116 within apredetermined period of time. For example, in some embodiments, tetheredmonitoring device 116 includes a timer that tracks a period of timebetween receiving check-in requests from tethered monitoring device 116and stores a predetermined period of time in a memory. Tetheredmonitoring device 116 determines that communications have beeninterrupted based on, for example, the timer reaching the predeterminedperiod of time without having received a check-in request from tetheredmonitoring device 116.

In some embodiments, the back-up communication subsystem, by default, isdeactivated to save battery usage. But upon activation (e.g., inresponse to an interruption in communication with the check-inapplication), the back-up communication subsystem allows directcommunications between monitoring center 130 and tethered monitoringdevice 116. In some embodiments, the back-up communication subsystemcommunicates to monitoring center 130 over a cellular network such as aglobal system for mobile communication (GSM) network, a code divisionmultiple access (CDMA) network, a 3G network, a 4G network, a 5G networkor any successor cellular network. In some embodiments, the back-upcommunication subsystem communicates to monitoring center 130 over Wi-Fito router 118 (if available). Yet in further embodiments, the back-upcommunication subsystem implements a GPS function that enablesmonitoring center 130 to receive location information (e.g., GPScoordinates) from tethered monitoring device 116.

In some embodiments, the connection between tethered mobile device 112and monitoring center 130 is routed through router 118 and employs awireless network such as Wi-Fi includes any or all of a Local-AreaNetwork (LAN), a Wide-Area Network (WAN), or the Internet. In someembodiments, the connection between tethered mobile device 112 andmonitoring center 130 is implemented through a cellular network such asa GSM network, a CDMA network, a 3G network, a 4G network, a 5G networkor any successor cellular network.

In some embodiments, jurisdictions provide tethered mobile devices 112,114, 122, and 124 for use by the user to be monitored by tetheredmonitoring system 100. In such embodiments, tethered mobile devices 112,114, 122, and 124 includes the check-in application pre-installed priorto providing it to the users. In some embodiments, tethered mobiledevices 112, 114, 122, and 124 are owned by the users but their releasefrom custody or a controlled environment is conditioned uponinstallation of the check-in application. Whether tethered mobile device112 is provided by monitoring center 140 or owned by user, tetheredmobile device 112 operates similarly to monitor the users as describedin various embodiments above and are remotely managed and updated bymonitoring center 130. As previously described, in addition to allowingactions and locations of users to be monitored, the check-in applicationenables administrators to remotely access, configure, and otherwisecontrol operations of tethered mobile device 112.

Exemplary Monitored Conference Device

FIG. 2 illustrates a block diagram of an exemplary tethered mobiledevice for use in the exemplary tethering monitoring system of FIG. 1,according to embodiments of the present disclosure. Tethered mobiledevice 200 represents an exemplary embodiment of tethered mobile device112 as described in FIG. 1. For ease and simplicity, the embodiment willbe further discussed with regard to tethered mobile device 112. However,it is to be understood that such discussion also applies to tetheredmobile devices 114, 122, or 124. In some embodiments, tethered mobiledevice 200 includes processor circuitry 210, communication interfaces220, and check-in subsystem 230.

Processor circuitry 210 includes one or more processors 212 and memory214. The number of processors 212 can be scaled to match the number ofsimultaneous user connections desired to be supported by a tetheringmonitoring system such as tethering monitoring system 100 of FIG. 1.Processors 212 control the operation of tethered mobile device 200 andits components. In some embodiments, memory 214 can be any well-knownvolatile and/or non-volatile memory that is removable and/ornon-removable. Memory 214 can store user preferences, user profiles, andother information regarding tethered mobile device 200. User profilescan include historical information regarding actions and movement oftethered mobile device 200. For example, actions include responsesreceived from tethered monitoring device 116 in response to check-inrequests. Movement of tethered mobile device 200 includes routestravelled by tethered monitoring device 116 and/or tethered mobiledevice 200. In some embodiments, user profiles also contain a list ofpreapproved or restricted destinations and routes that the user cantake. For example, the list could include approved locations such as theuser's doctor's office and a supermarket. Approved or restricted routesrefer to roads or paths that can be or cannot be included in a tripitinerary that is generated for the user. One reason for restrictingcertain roads is to prevent a user from driving by a certain location.For example, a rehabilitating drug user can be steered away from areasof a city that are known to have drug dealers.

In some embodiments, communication interfaces 220 includes one or moretransceivers, transmitters, and/or receivers that communicate via awireless interface 222, such as Wi-Fi interface 223, cellular interface224, Bluetooth interface 225, radiofrequency (RF) interface 226. Wi-Fiinterface 223 includes a Wi-Fi transceiver that enables Wi-Ficommunication between tethered mobile device 200 and an external devicethat also has Wi-Fi capability such as router 118 or tethered monitoringdevice 116. Cellular interface 224 includes a cellular transceiver thatenables cellular communication between tethered mobile device 200 and anexternal device that has cellular capability such as cellular antennathat can route communications to monitoring center 130. Bluetoothinterface 225 includes a Bluetooth transceiver that enables Bluetoothcommunication between tethered mobile device 200 and an external devicethat also has Bluetooth capability, such as an access point or tetheredmonitoring device 116. RF interface 226 includes a RF transceiver thatenables RF communication tethered mobile device 200 and an externaldevice that has RF capability such as tethered monitoring device 116.

Check-in subsystem 230 includes components that enables the check-in andtethered functionality of tethered mobile device 200. Check-in subsystem230 includes check-in component 232, security component 234, trackingcomponent 236, and secure area 238. In some embodiments, check-incomponent 232 implements a check-in application 239 installed in securearea 238. In some embodiments, check-in application 239 is provided bymonitoring center 130. In some embodiments, secure area 238 isimplemented as a private container in a file system of tethered mobiledevice 200. A private container is a portion of the file system intethered mobile device 200 that cannot be accessed by a user of tetheredmobile device 200 but can be accessed by an administrator or monitoringcenter 130. In other words, the user of tethered mobile device 200grants a third party such as monitoring center 130 remote access totethered mobile device 200 and monitoring center 130 has control over aportion of the file system. In this manner, secure area 238 is securedfrom access by a user of tethered mobile device 200. Accordingly, anyfiles or applications stored in secure area 238 cannot be modified oruninstalled unless by an authorized personnel of monitoring center 130.

Through check-in application 239, monitoring center 130 controlsoperations of tethered mobile device 200 by communicating with check-incomponent 232 such as through control messages that operates behavior ofcheck-in application 239. Upon detecting n appropriate condition (e.g.,a control message from monitoring center 130, a scheduled time),check-in application 239 initiates a check-in procedure on tetheredmobile device 200. As discussed above, the check-in procedure includessubmitting check-in requests to either tethered monitoring device 116and/or for display on tethered mobile device 200. In some embodiments,the check-in requests require responses from tethered monitoring device116 and/or the user of tethered mobile device 200.

In some embodiments, check-in component 232 ensures that tetheredmonitoring device 116 is still within a certain proximity to tetheredmobile device 200 by responses (or the lack thereof) from tetheredmonitoring device 116. Check-in component 232 receives responses fromtethered monitoring device 116 and is responsible for validating theresponses to ensure that communications received from tetheredmonitoring device 116 have the appropriate identifier and/or areresponsive to the check-in requests. By executing the check-inprocedure, check-in component 232 monitors and tracks the presence oftethered monitoring device 116 and, indirectly, the user of tetheredmobile device 200 and tethered monitoring device 116.

In some embodiments, check-in subsystem 230 manages Wi-Fi interface 223and cellular interface 224. For example, in some embodiments, whenavailable, check-in subsystem 230 maintains a Wi-Fi connection betweenWi-Fi interface 223 and monitoring center 130. Check-in subsystem 230uses the Wi-Fi connection to allow monitoring center 130 to maintaincontrol over tethered mobile device 200. For example, check-in subsystem230 can transmit and receive control messages during a check-inprocedure from monitoring center 130 and is programmed to disablecertain operations of tethered mobile device 200 upon detection ofcertain conditions such as but not limited to detecting an interruptionof communications between tethered mobile device 200 and monitoringcenter 130 over the Wi-Fi connection, receiving a command frommonitoring center 130, and detecting any attempts to compromise tetheredmobile device 200. For example, check-in subsystem 230 may detectcontrol messages from monitoring center 130 or security component 234 todisable all communications and/or operations of tethered mobile device200 until a response to a check-in request has been received andverified. As another example, check-in component 232 periodically and/orat predetermined intervals receives control messages from monitoringcenter 130; check-in component 232 disables all operations of tetheredmobile device 200 until additional control messages are received. Insome embodiments, disabling operations of tethered mobile device 200includes but is not limited to disabling communication interfaces 220,disabling access to certain portions of memory 214, and shutting downtethered mobile device 200.

In some embodiments, check-in subsystem 230 provide tracking informationto monitoring center 130 regarding activities performed by tetheredmobile device 200. Such information includes historical information ofthe tethered mobile device 200 such as locations visited by tetheredmobile device and communications between tethered mobile device 200 andtethered monitoring device 116. In some embodiments, the trackinginformation is transmitted periodically such as on a predeterminedschedule. In other embodiments, the tracking information is transmittedupon a request from monitoring center 130.

In some embodiments, security component 234 implements a securityapplication that maintains security of tethered mobile device 200 toprevent a user from compromising or tampering with tethered monitoringdevice 116, tethered mobile device 200, and tethered monitoring system100. Security component 234 implements security protocols such asauthentication of users of tethered mobile device 200, authenticatingcommunications between tethered mobile device 200 and tetheredmonitoring device 116, and restricting user access to any secure areasof tethered mobile device 200. In some embodiments, security component234 authenticates users utilizing identity data which includes but isnot limited to at least one of a username and password data, challengequestions, challenge answers, biometric data, device data such as makeand model of a communication device, and/or location data. Biometricdata includes one or more of a finger print, a hand print, a voicesample, an iris or retinal sample, an image of the user (2D or 3D), ahand geometry, a signature identification, an infrared cameraidentification, or any other biometric as deemed appropriate. Thechallenge question form of identity data may be a series of challengequestions, or a single challenge question such as the last four digitsof a user's social security number, mother's maiden name, and the like.Security component 234 is further configured to facilitate a securecommunication between tethered mobile device 200 and tethered monitoringdevice 116 by performing authentication of communications. Theauthentication includes determining that communications contain expectedidentifiers identifying the source of communications.

In some embodiments, tracking component 236 implements a trackingapplication that reports location and positioning information oftethered mobile device 200 to monitoring center 130. In someembodiments, tracking component 236 further includes GPS circuitry toretrieve location information, such as GPS coordinates, of tetheredmobile device 200. Tracking component 236 also implements a mappingapplication that either provides mapping functionality or controlsoperations of another mapping application installed on tethered mobiledevice 200. The tracking application and the mapping applicationcoordinate communications to provide navigation (e.g., directions)information to the user and provide real-time or near-real-time locationinformation to monitoring center 130.

For example, the mapping application receives destination informationfrom the user of tethered mobile device 200 or monitoring center 130. Insome embodiments, the user has to submit, for preapproval, destinationinformation to monitoring center 130. If approved, monitoring center 130transmits the destination information to tracking component 236 whichthen generates mapping information from the current location of tetheredmobile device 200 to the approved destination information. In someembodiments, monitoring center 130 generates and provides the mappinginformation to tethered mobile device 200 after approving thedestination information. In some embodiments, the mapping information isan authorized route between the current location and the approveddestination information. The tracking application then tracks thelocation of tethered mobile device 200 to ensure that it follows themapping information. For example, the tracking application transmits thelocation information to monitoring center 130 so that the movements oftethered mobile device 200 can be compared with the generated mappinginformation. In other embodiments, tracking component 236 verifies thattethered mobile device 200 is following the generated mappinginformation. Tracking component 236 also communicates with securitycomponent 234 to generate alerts and/or notifications to monitoringcenter 130 and for display on tethered mobile device 200 when tetheredmobile device 200 is determined to be moving off of the generatedmapping information.

Exemplary Tethered Monitoring Device

FIG. 3 illustrates a block diagram of tethered monitoring device 300,according to embodiments of the present disclosure. In an embodiment,tethered monitoring device 300 represents an exemplary embodiment oftethered monitoring device 116 of FIG. 1. Tethered monitoring device 300includes but is not limited to processor subsystem 310, communicationinterfaces 320, and tethering subsystem 330. Tethered monitoring device300 communicates with tethered mobile device 200. In some embodiments,tethered monitoring device 300 is semi-permanently attached to a user oftethered mobile device. Semi-permanently means that tethered monitoringdevice 300 can only be removed under certain conditions such as througha key or a remote signal (e.g., from monitoring center 130). In someembodiments, tethered monitoring device 300 is implemented as an ankleor wrist band.

Processor subsystem 310 includes one or more processors 312 and memory314. The number of processors can be scaled to match the number ofsimultaneous user connections desired to be supported by a tetheringmonitoring system such as tethering monitoring system 100 of FIG. 1.Processor 312 manages operations of tethered monitoring device 300 andmemory 314 stores applications for controlling the operations.

Communication interface 320 includes Wi-Fi interface 322, Bluetoothinterface 324, and RF interface 326. Communication interface 320 alsoincludes back-up interfaces 328 which includes cellular interface 327and GPS interface 329. In some embodiments, back-up interfaces 328 areinactive in order to conserve battery usage of tethered monitoringdevice 300. In some embodiments, monitoring center 130 and/or tetheredmobile device 200 will activate cellular interface 327 and/or GPSinterface 329 when communications between tethered monitoring device 300and monitoring center 130 and/or tethered mobile device 200 areinterrupted. Activating cellular interface 327 or GPS interface 329allows tethered monitoring device 300 to be located independently of anycommunications between monitoring center 130 and/or tethered mobiledevice 200. In other words, under normal operations, in someembodiments, monitoring center 130 and/or tethered mobile device 200track the location of tethered monitoring device 300 through any one ofWi-Fi interface 321, Bluetooth interface 323, and RF interface 325.

Tethering subsystem 330 includes user profile 332, check-in generator334, and security identifier 336. Tethering subsystem 330 is responsiblefor communicating responses and providing tracking information relatedto tethered monitoring device 300 to both monitoring center 130 andtethered mobile device 200. User profile 332 stores information relatedto the user of tethered monitoring device 300 including the user'sidentification information, security protocols associated with the user,historical information regarding the user's actions related to tetheredmonitoring device 300.

Check-in generator 334 generates responses to check-in requests receivedfrom tethered mobile device 200 and/or monitoring center 130. Check-inrequests are either automatic or manual check-in requests. Manualcheck-in requests include but are not limited to questions that requireinput from the user (e.g., such as a math problem or question with aresponse that is likely known only to the user) or specific operationsto be performed by the user using tethered mobile device 112. Automaticrequests include requests to tethered monitoring device 300 for whichcheck-in generator 334 automatically generates responses. Automaticcheck-in requests include but are not limited to heartbeat messages,encrypted messages, and requests for responses that include a uniqueidentifier, such as security identifier 336, associated with tetheredmonitoring device 300. In some embodiments, security identifier 336 is aunique alphanumeric value specific to tethered monitoring device 300.

In some embodiments, tethering subsystem 330 also allows for thedownload of software and updates from monitoring center 130 and/ortethered mobile device 200 to tethered monitoring device 300. Forexample, tethering subsystem 330 receives over-the-air wireless updates.In some embodiments, tethering subsystem 330 also performsauthentication functions for communications between tethered monitoringdevice 300 and monitoring center 130 and/or tethered mobile device 200.Authentication functions include encrypting and decryptingcommunications and information transmitted from and received by tetheredmonitoring device 300.

Exemplary Tethering Monitoring System Operation

Exemplary usage of tethering monitoring system 100, tethered mobiledevice 200, and tethered monitoring device 300 will be described withrespect to FIGS. 4-7. The exemplary usage described in FIGS. 4-7 can beperformed by processing logic that can comprise hardware (e.g.,circuitry, dedicated logic, programmable logic, microcode, etc.),software (e.g., instructions executing on a processing device), or acombination thereof. For illustrative purposes, FIGS. 4-7 are describedwith respect to FIGS. 1-3 but are not limited to these exampleembodiments. The methods described in FIGS. 4-7 can be performed byprocessing logic that can comprise hardware (e.g., circuitry, dedicatedlogic, programmable logic, microcode, etc.), software (e.g.,instructions executing on a processing device), or a combinationthereof. It is to be appreciated that additional steps, such asadditional object recognition steps, may be performed. Moreover, not allsteps may be needed to perform the disclosure provided herein. Further,some of the steps may be performed simultaneously, or in a differentorder than shown in FIGS. 4-7, as will be understood by a person ofordinary skill in the art. Additionally, some steps can be combined withsteps of methods from other figures and performed as a single step.

FIG. 4 illustrates a flowchart diagram of an exemplary method forexecuting a check-in procedure in an exemplary tethered mobile device ofFIG. 2, according to embodiments of the present disclosure. In someembodiments, method 400 can be performed by tethered mobile device 200,and in particular, check-in application 239 that is installed in securearea 238 of check-in subsystem 230. For the purposes of discussionbelow, method 400 is discussed with respect to tethered mobile device200 but can be performed by other devices as well.

In 402, tethered mobile device 200 initiates a check-in procedure. Asdescribed above, the check-in procedure allows tethered mobile device200 to determine whether a user is within a certain proximity oftethered mobile device 200. The check-in procedure includes requeststransmitted from tethered mobile device 200 and responses from eitherthe user or tethered monitoring device 300 that is attached to the user.In some embodiments, monitoring center 130 initiates the requests to betransmitted from tethered mobile device 200.

In 404, tethered mobile device 200 determines whether to initiate amanual or automatic check-in request. Responses to a manual check-inrequest include user actions or user inputs received from a user throughtethered mobile device 200 such as through interacting with a displayedGUI by check-in application 239. Responses to an automatic check-inrequest include automated responses from tethered monitoring device 300and do not require user input or action. An action request is a requestfor the user to perform an action such as utilize the camera of tetheredmobile device 200, respond to on-screen prompts, or otherwise utilizetethered mobile device 200 in a manner specified by the GUI.

In 406, tethered mobile device 200 determines that the check-inprocedure is transmitting a manual check-in request and displays themanual check-in request such as through a GUI of check-in application239. As discussed above, the manual check-in request includes requestsfor a user to provide inputs to questions or to perform actions such asprovide a picture of a certain object (e.g., tethered monitoring device300) or biometric information such as a fingerprint of the user, animage of the user, or a voice sample. In some embodiments, the type ofrequest is random so that the user cannot predict what requests will bedisplayed to the user. This is to prevent the user from preparingresponses so that other users can attempt to respond to the requests.For example, the user may attempt to circumvent the check-in procedureby providing a picture, a voice recording, and other images to anotheruser. Randomizing the requests prevents these attempts. In addition torandomizing the type of request, the content of the request can berandomized as well. For example, the manual check-in request couldinclude a random phrase for the user to repeat (instead of a phrase thatrepeats for each request), a picture of a random object such as thetethered monitoring device 300, any physical marks on the user (e.g., atattoo), or an object known to be in the user's room (e.g., a clock).

In 408, tethered mobile device 200 receives a response in the form of auser input or action from the user. In some embodiments, the userinteracts with a GUI provided by check-in application 239 in order toprovide the user input or action in response to the displayed check-inrequest. In 410, tethered mobile device 200 validates the response bydetermining whether the response matches an expected response to thedisplayed manual check-in request. In other words, it is determinedwhether the response is a valid or invalid check-in response. Forexample, a response to a manual check-in request for a user's biometricinformation would be compared with biometric information associated withthe user. In some embodiments, a user's biometric information and/or“correct” responses to check-in requests are stored in secure area 238of tethered mobile device 200. When a response includes voice samples ofthe user, check-in application 239 performs voice analysis to determineboth that the voice sample is of the user of tethered mobile device 200and that the voice sample includes the correct word or phrase to berepeated by the user. For example, a manual check-in request couldrequire the user to say the date and time at which the manual check-inrequest was displayed. Accordingly, check-in application 239 validates aresponse by determining that the voice sample accurately states the dateand time. In other embodiments, a user's biometric information is storedat monitoring center 130 and responses to check-in requests aretransmitted from tethered mobile device 200 to monitoring center 130 forcomparison and validation.

In 412, if the response is not valid, tethered mobile device 200 sendsan alert notification to monitoring center 130. The alert notificationinforms administrators and jurisdictions that the user could beviolating terms of the user's release. Appropriate action such ascalling tethered mobile device 200 in an attempt to contact the user,sending authorities to the detected location of tethered mobile device200 and/or the detected location of tethered monitoring device 300.

In 414, if the response is valid, tethered mobile device 200 determineswhether any additional verification is necessary. For example, certainuser profiles can indicate that users require more than type ofverification based on a user history or by request of a jurisdiction whowishes more careful screening of its users.

In 416, if additional verification is determined to be necessary or ifthe check-in request is determined to be an automatic check-in request,check-in application 239 generates a check-in request. In 418, tetheredmobile device 200 transmits the generated automatic check-in request totethered monitoring device 300. In some embodiments, the automaticcheck-in request is a request for tethered monitoring device 300 torespond with a unique device identifier associated with tetheredmonitoring device 300.

In 420, tethered mobile device 200 receives a response to the automaticcheck-in request from tethered monitoring device 300. In 422, tetheredmobile device 200 determines whether the received response is valid oralternatively determines that no response is received. If the responseis not valid or if no response is received at all, tethered mobiledevice 200 transmits an alert notification to monitoring center 130, in412.

FIG. 5 illustrates a flowchart diagram of an exemplary method fortracking an authorized trip itinerary for the exemplary tethered mobiledevice of FIG. 2 in the exemplary tethering monitoring system of FIG. 1,according to embodiments of the present disclosure. Method 500 can beperformed by tethered mobile device 200 and monitoring center 130.

In 502, tethered mobile device 200 receives a trip request from a userthat desires to make a trip from his current location or a designatedlocation to which the user is confined. In some embodiments, the user ison house arrest, and the designated location of the user will be theuser's house. The trip request includes a destination such as anaddress. In some embodiments, check-in application 239 displays a routeGUI that allows the user to enter trip information such as a currentlocation (if not a designated location) and a destination. Tetheredmobile device 200 receives the trip information and determines whetherto approve or deny the trip request. There is either automatic or manualapproval of the trip request. In some embodiments, tethered mobiledevice transmits it to monitoring center 130 for approval in 504. Withautomatic approval, monitoring center 130 and/or tethered mobile device200 store a list of preapproved destinations to which the user maytravel. For example, administrators of the jurisdiction preapprove thedestinations which are submitted in advance by the user. For example,the user will provide his doctor's office, a significant other's home,the supermarket to the jurisdiction which can be approved and enteredinto a list which is stored as part of the user's profile. In someembodiments, the trip information can be approved within check-inapplication 239 and does not need to be transmitted to be monitoringcenter 130. For example, check-in application 239 checks the user'sprofile for a list of approved or restricted locations when determiningwhether to approve the trip information and generating a trip itineraryto route the user to the destination. With manual approval, the tripinformation is routed to an authorized administrator for approval.

In 504, if the trip information is transmitted to monitoring center 130,monitoring center 130 determines whether to approve the trip informationbased on the user profile and any other criteria related to the user. Inother embodiments, if the trip information is analyzed at tetheredmobile device 200, then tethered mobile device 200 determines whether toapprove the trip information. In 506, monitoring center 130 (or tetheredmobile device 200) generates the trip itinerary based on the approvedtrip information. In some embodiments, the trip itinerary is a route forthe user to follow from the current location of tethered mobile device200 to the requested destination. The trip itinerary is provided totethered mobile device 200.

In 508, tethered mobile device 200 receives the generated trip itineraryand displays it for the user. Check-in application 239 detects that theuser has initiated the trip such as by detecting that the user hasstarted along the generated trip itinerary. In 510, check-in application239 tracks the route taken by tethered mobile device 200. Tracking theposition of tethered mobile device 200 includes but is not limited toreceiving location information (e.g., GPS coordinates). In 512, check-inapplication 239 determines whether tethered mobile device 200 isfollowing or deviating from the generated trip itinerary based on thetracked route in 510.

If not, in 514, tethered mobile device 200 transmits an alertnotification to alert monitoring center 130 as to the deviation from thegenerated trip itinerary. In 516, tethered mobile device 200 hasdetermined that it is following the generated trip itinerary and nowdetermines whether to perform an additional check-in procedure toconfirm that the user is with the tethered mobile device 200. If not,tethered mobile device 200 continues tracking the travel route in 510.In 518, a check-in procedure is performed similar to what is discussedwith respect to FIG. 4.

FIG. 6 illustrates a flowchart diagram of an exemplary method fordetermining when to initiate a check-in procedure in the exemplarytethering monitoring system of FIG. 1, according to embodiments of thepresent disclosure. In some embodiments, method 600 is performed bytethered mobile device 200 or monitoring center 130.

In 602, tethered mobile device 200 and/or monitoring center 130 initiatea monitoring operation of tethered mobile device 200 to determinewhether to initiate the check-in procedure, such as what is describedwith respect to FIG. 4. In some embodiments, initiating monitoring isperformed on an automated basis such as on a predetermined schedule(e.g., every 2 minutes). In some embodiments, initiating monitoring isperformed on a manual basis such as manually initiated by an authorizedadministrator at monitoring center 130. In some embodiments, initiatingmonitoring is a combination of automated and manual procedures.

In 604-610, certain conditions are checked during the monitoringoperation to determine whether to initiate a check-in request.Conditions include but are not limited to a schedule condition and atimeout condition. While certain conditions are discussed in 604-610,other conditions are within the scope of the disclosure. For example, atimeout condition indicates that tethered mobile device 200 has notcommunicated with monitoring center within a predetermined time period.In 604, it is determined whether tethered mobile device 200 has movedwithin a predetermined time period from its current location. In someembodiments, monitoring center 130 sets the time period by transmittinga threshold value for storing in tethered mobile device 200. Thethreshold value represents the predetermined time period. In someembodiments, the time period also involves a specific time of day suchas during the daytime or night time hours. For example, it is morelikely that tethered mobile device 200 will not be moved while the useris sleeping. However, if tethered mobile device 200 has not moved withina threshold period of time (e.g., 3 hours) during the day, this activitywould be more suspicious and could indicate that the user has lefttethered mobile device 200 so that the user cannot be tracked.

If tethered mobile device 200 has moved within the predetermined timeperiod, then the monitoring operation moves to 606. In 606, it isdetermined whether a check-in procedure has been performed within apredetermined time period. This is a schedule condition. In someembodiments, monitoring center 130 sets the value for the time periodand transmits the value for storing in tethered mobile device 200. Forexample, monitoring center 130 can establish that a check-in procedureshould be performed on a schedule such as every 15 minutes.

If the check-in procedure has been performed within the predeterminedtime period, the monitoring operation moves to 608. In 608, it isdetermined whether tethered mobile device 200 is detected to be outsideof a defined area such as the user's home. If tethered mobile device 200is determined to be outside of the defined area by a predetermineddistance, the monitoring operation initiates the check-in procedure. Ifnot, in 610, the monitoring operation determines whether to initiate arandom check-in request with tethered mobile device 200. If theconditions of 604-610 do not indicate that the check-in procedure shouldbe performed, then the monitoring operation continues to check theconditions. Otherwise, in 612, tethered mobile device 200 transmits acheck-in request and initiates a check-in procedure such as the check-inprocedure that is described with respect to FIG. 4.

FIG. 7 illustrates a block diagram of an of an exemplary method forperforming a manual check-in request of a monitored person in anexemplary tethered mobile device of FIG. 2 in the exemplary tetheringmonitoring system of FIG. 1, according to embodiments of the presentdisclosure. Method 700 can be performed by tethered mobile device 200.

In 702, tethered mobile device 200 determines that a manual check-inrequest is to be performed. In 704, tethered mobile device 200determines whether to perform a biometric manual check-in request.Examples of biometric manual check-in requests include but are notlimited to fingerprint verification, voice verification, and/or facialrecognition. If yes, in 706, tethered mobile device 200 initiates thedetermined biometric verification. In some embodiments, check-inapplication 239 provides a GUI with which the user interacts to providethe requested biometric information.

In 708, tethered mobile device 200 determines whether to a picturemanual check-in request. Examples of picture manual check-in requestsinclude requesting the user to take a picture of a specific object suchas the user's tethered monitoring device 300 or an identifying mark onthe user such as a tattoo. If yes, in 710, tethered mobile device 200initiates the determined picture manual check-in request. In someembodiments, check-in application 239 displays the request on the GUI oftethered mobile device 200.

In 712, tethered mobile device 200 determines whether manual check-inrequest is a quiz. Examples of quizzes include questions to be answeredby the user such as mathematical questions, personal questions relatedto the user, and identification questions (e.g., requesting the user toidentify a displayed image). If yes, in 714, tethered mobile deviceinitiates the quiz. In some embodiments, check-in application 239provides a GUI with which the user provides a response to the quiz.

In 716, tethered mobile device 200 calls a designated phone number inorder to allow the user to manually check-in using a telephone call. Forexample, the designated phone number is of monitoring center 130 andrequires the user to talk with an authorized official at monitoringcenter 130 in order to check-in.

In 718, if a manual check-in request is performed that results in aresponse being received from the user. In some embodiments, the responseis received by check-in application 239. In some embodiments, theresponse is transmitted from tethered mobile device 200 to monitoringcenter 130. In 720, the received response is determined whether to be avalid or invalid check-in response and the received response isvalidated. In 722 if the response is not valid, tethered mobile device200 transmits a notification that indicates the response is not valid.

Exemplary Computer Implementation

It will be apparent to persons skilled in the relevant art(s) thatvarious elements and features of the present disclosure, as describedherein, can be implemented in hardware using analog and/or digitalcircuits, in software, through the execution of computer instructions byone or more general purpose or special-purpose processors, or as acombination of hardware and software.

The following description of a general purpose computer system isprovided for the sake of completeness. Embodiments of the presentdisclosure can be implemented in hardware, or as a combination ofsoftware and hardware. Consequently, embodiments of the disclosure maybe implemented in the environment of a computer system or otherprocessing system. For example, the methods of FIGS. 4-7 can beimplemented in the environment of one or more computer systems or otherprocessing systems. An example of such a computer system 800 is shown inFIG. 8. One or more of the modules depicted in the previous figures canbe at least partially implemented on one or more distinct computersystems 800.

Computer system 800 includes one or more processors, such as processor804. Processor 804 can be a special purpose or a general purpose digitalsignal processor. Processor 804 is connected to a communicationinfrastructure 802 (for example, a bus or network). Various softwareimplementations are described in terms of this exemplary computersystem. After reading this description, it will become apparent to aperson skilled in the relevant art(s) how to implement the disclosureusing other computer systems and/or computer architectures.

Computer system 800 also includes a main memory 806, preferably randomaccess memory (RAM), and may also include a secondary memory 808.Secondary memory 808 may include, for example, a hard disk drive 810and/or a removable storage drive 812, representing a floppy disk drive,a magnetic tape drive, an optical disk drive, or the like. Removablestorage drive 812 reads from and/or writes to a removable storage unit816 in a well-known manner. Removable storage unit 816 represents afloppy disk, magnetic tape, optical disk, or the like, which is read byand written to by removable storage drive 812. As will be appreciated bypersons skilled in the relevant art(s), removable storage unit 816includes a computer usable storage medium having stored therein computersoftware and/or data.

In alternative implementations, secondary memory 808 may include othersimilar means for allowing computer programs or other instructions to beloaded into computer system 800. Such means may include, for example, aremovable storage unit 818 and an interface 814. Examples of such meansmay include a program cartridge and cartridge interface (such as thatfound in video game devices), a removable memory chip (such as an EPROM,or PROM) and associated socket, a thumb drive and USB port, and otherremovable storage units 818 and interfaces 814 which allow software anddata to be transferred from removable storage unit 818 to computersystem 800.

Computer system 800 may also include a communications interface 820.Communications interface 820 allows software and data to be transferredbetween computer system 800 and external devices. Examples ofcommunications interface 820 may include a modem, a network interface(such as an Ethernet card), a communications port, a PCMCIA slot andcard, etc. Software and data transferred via communications interface820 are in the form of signals which may be electronic, electromagnetic,optical, or other signals capable of being received by communicationsinterface 820. These signals are provided to communications interface820 via a communications path 822. Communications path 822 carriessignals and may be implemented using wire or cable, fiber optics, aphone line, a cellular phone link, an RF link and other communicationschannels.

As used herein, the terms “computer program medium” and “computerreadable medium” are used to generally refer to tangible storage mediasuch as removable storage units 816 and 818 or a hard disk installed inhard disk drive 810. These computer program products are means forproviding software to computer system 800.

Computer programs (also called computer control logic) are stored inmain memory 806 and/or secondary memory 808. Computer programs may alsobe received via communications interface 820. Such computer programs,when executed, enable the computer system 800 to implement the presentdisclosure as discussed herein. In particular, the computer programs,when executed, enable processor 804 to implement the processes of thepresent disclosure, such as any of the methods described herein.Accordingly, such computer programs represent controllers of thecomputer system 800. Where the disclosure is implemented using software,the software may be stored in a computer program product and loaded intocomputer system 800 using removable storage drive 812, interface 814, orcommunications interface 820.

In another embodiment, features of the disclosure are implementedprimarily in hardware using, for example, hardware components such asapplication-specific integrated circuits (ASICs) and gate arrays.Implementation of a hardware state machine so as to perform thefunctions described herein will also be apparent to persons skilled inthe relevant art(s).

CONCLUSION

It is to be appreciated that the Detailed Description section, and notthe Abstract section, is intended to be used to interpret the claims.The Abstract section may set forth one or more, but not all exemplaryembodiments, and thus, is not intended to limit the disclosure and theappended claims in any way.

The disclosure has been described above with the aid of functionalbuilding blocks illustrating the implementation of specified functionsand relationships thereof. The boundaries of these functional buildingblocks have been arbitrarily defined herein for the convenience of thedescription. Alternate boundaries may be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

It will be apparent to those skilled in the relevant art(s) that variouschanges in form and detail can be made therein without departing fromthe spirit and scope of the disclosure. Thus, the disclosure should notbe limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. A method for providing tethering-basedmonitoring, comprising: receiving an indication to initiate a check-inprocedure on a tethered mobile device; initiating, based on theindication, the check-in procedure on the tethered mobile device,wherein the check-in procedure comprises: transmitting, to the tetheredmobile device, at least one of a real-time verification request that isconfigured to be displayed on the tethered mobile device and a check-inrequest that is configured to be transmitted from the tethered mobiledevice to a tethered monitoring device; receiving a response to the atleast one of the real-time verification request and the check-inrequest; and performing a validation of the response, wherein thevalidation includes determining whether the response includes averification response to the real-time verification request or acheck-in response to the check-in request; and performing a follow-upaction based on the validation of the response.
 2. The method of claim1, wherein the follow-up action includes transmitting an alertnotification to a monitoring center in response to the validation of theresponse indicating an invalid verification response or an invalidcheck-in response.
 3. The method of claim 1, wherein the real-timeverification request includes an identity check of a user of thetethered mobile device, the identity check including at least one of abiometric check of the user and an action request, wherein the actionrequest includes a request for the user to perform an action.
 4. Themethod of claim 3, further comprising: determining that a response tothe identity check is not received within a predetermined responseperiod; and transmitting an alert notification to a monitoring center inresponse to the determining.
 5. The method of claim 1, wherein thecheck-in request includes a request for the tethered monitoring deviceto include a device identifier in the check-in response transmitted tothe tethered mobile device and wherein performing the validationincludes validating the device identifier in the check-in response. 6.The method of claim 1, further comprising: generating, by the tetheredmobile device, the indication based on at least one of a timeoutcondition indicating that the tethered mobile device has not movedwithin a predetermined time period, and a schedule condition indicatingthat the check-in procedure is to be performed after the predeterminedtime period.
 7. The method of claim 1, further comprising: transmitting,to a monitoring center, a trip request, wherein the trip requestincludes a current location of the tethered mobile device and adestination; and receiving, from the monitoring center, a trip itineraryin response to the trip request, wherein the trip itinerary includes aroute from the current location to the destination.
 8. The method ofclaim 7, further comprising: determining that the tethered mobile devicehas moved away from the current location; tracking an updated locationof the tethered mobile device; determining whether the updated locationis on the route; and transmitting an alert notification to themonitoring center based on determining that the updated location is noton the route.
 9. A tethered mobile device, comprising: a memory; and aprocessor coupled to the memory, the memory configured to store programcode that when executed by the processor causes operations to beperformed, the operations comprising: transmitting, to a monitoringcenter, a trip request, wherein the trip request includes a currentlocation of the tethered mobile device and a destination; receiving,from the monitoring center, a trip itinerary in response to the triprequest, wherein the trip itinerary includes a route from the currentlocation to the destination; receiving, from the monitoring center, anindication to initiate a check-in procedure on the tethered mobiledevice in response to the tethered mobile device moving to an updatedlocation along the route; initiating, based on the indication, thecheck-in procedure on the tethered mobile device, wherein the check-inprocedure comprises: receiving, from the monitoring center, at least oneof a real-time verification request that is configured to be displayedon the tethered mobile device and a check-in request that is configuredto be transmitted from the tethered mobile device to a tetheredmonitoring device; and transmitting, to the monitoring center, aresponse to the at least one of the real-time verification request andthe check-in request; performing a validation of the response, whereinthe validation includes determining whether the response includes averification response or a check-in response; and performing a follow-upaction based on the validation of the response.
 10. The tethered mobiledevice of claim 9, wherein the follow-up action includes transmitting analert notification to the monitoring center in response to thevalidation of the response indicating an invalid verification responseor an invalid check-in response.
 11. The tethered mobile device of claim9, wherein the real-time verification request includes an identity checkof a user of the tethered mobile device, the identity check including atleast one of a biometric check of the user and an action request,wherein the action request includes a request for the user to perform anaction.
 12. The tethered mobile device of claim 11, the operationsfurther comprising: determining that a response to the identity check isnot received within a predetermined response period; and transmitting analert notification to the monitoring center in response to thedetermining.
 13. The tethered mobile device of claim 12, wherein thecheck-in request includes a request for the tethered monitoring deviceto include a device identifier in the check-in response transmitted tothe tethered mobile device and wherein performing the validationincludes validating the device identifier in the check-in response. 14.The tethered mobile device of claim 13, the operations furthercomprising: generating the indication based on at least one of a timeoutcondition indicating that the tethered mobile device has not movedwithin a predetermined time period, and a schedule condition indicatingthat the check-in procedure is to be performed after the predeterminedtime period.
 15. The tethered mobile device of claim 12, the operationsfurther comprising: determining that the tethered mobile device hasmoved away from the current location; tracking the updated location ofthe tethered mobile device; determining whether the updated location ison the route; and transmitting the alert notification to the monitoringcenter based on determining that the updated location is not on theroute.
 16. A non-transitory computer-readable medium having instructionsstored therein, which when executed by a processor in a tethered mobiledevice, cause the processor to perform operations, the operationscomprising: receiving an indication to initiate a check-in procedure onthe tethered mobile device; initiating, based on the indication, thecheck-in procedure on the tethered mobile device, wherein the check-inprocedure comprises: transmitting, to the tethered mobile device, areal-time verification request that is configured to be displayed on thetethered mobile device; receiving a verification response to thereal-time verification request; and performing a first validation of theverification response, wherein the first validation comprisesdetermining whether the verification response includes an expectedresponse to the real-time verification request; and in response to thefirst validation, transmitting, to the tethered mobile device, acheck-in request that is configured to be transmitted from the tetheredmobile device to a tethered monitoring device; receiving, from thetethered monitoring device, a check-in response, wherein the check-inresponse includes a device identifier of the tethered monitoring device;performing a second validation of the check-in response, wherein thesecond validation comprises determining whether the check-in responseincludes the device identifier; and performing a follow-up action basedon the first and the second validation.
 17. The non-transitorycomputer-readable medium of claim 16, wherein the follow-up actionincludes transmitting an alert notification to a monitoring center inresponse to a validation of the response indicating an invalidverification response or an invalid check-in response.
 18. Thenon-transitory computer-readable medium of claim 16, wherein thereal-time verification request includes an identity check of a user ofthe tethered mobile device, the identity check including at least one ofa biometric check of the user and an action request, wherein the actionrequest includes a request for the user to perform an action.
 19. Thenon-transitory computer-readable medium of claim 18, the operationsfurther comprising: determining that a response to the identity check isnot received within a predetermined response period; and transmitting analert notification to a monitoring center in response to thedetermining.
 20. The non-transitory computer-readable medium of claim16, wherein the check-in request includes a request for the tetheredmonitoring device to include the device identifier in the check-inresponse transmitted to the tethered mobile device and whereinperforming the second validation includes validating the deviceidentifier in the check-in response.